Description

Roles

Attributes

Steps

1. Detail Use Cases and scenarios:

   Some Use Cases and scenarios may need to be described in more detail to validate our understanding of the requirement and to permit software development to begin. This does not imply that all use cases and scenarios will be detailed prior to commencing implementation. Collaborate with stakeholders to detail only those that are prioritized for implementation in the next iteration or two, or those that are deemed architecturally significant.

    

   The level of detail captured will vary depending upon the needs of the project and the complexity of the use case.

    

   Capture the use-case details in Use Case.

2. Detail Supporting Requirements:

   Some Supporting Requirements Specification may need to be clarified or described in more detail, new requirements may have been discovered as we detailed the use cases and scenarios, and new requirements may have been submitted as Change Requests. Collaborate with stakeholders to capture, refine and validate those requirements that will have an impact on near term work or are deemed architecturally significant.

    

   Capture these requirements in the Supporting Requirements Specification. For additional guidance on detailing supporting requirements see Supporting Requirements.

3. Detail Glossary terms:

   Review the flow of the use case or scenario. If information is exchanged, be specific about what is passed back and forth.Collaborate with stakeholders to ensure that you define newly discovered domain terms, or ambiguous terms properly in the Glossary. If your understanding of the domain has improved, refine existing glossary terms.

4. Update Use-Case Model:

   Based on your work update the Use-Case Model. Add, remove or update Actorsand Use Cases as required. For more information on creating and structuring your usecase model see Use-Case Model.

5. Achieve concurrence:

   Conduct a review of the requirements with relevant Stakeholders and the development team to ensure consistency with the Vision, assess quality, and identify required changes.

Inputs and Outputs

WorkProduct	Input	Output	Allowable States
Glossary			(none)
Iteration Plan			(none)
Supporting Requirements Specification			(none)
Use Case			(none)
Use-Case Model			(none)
Vision			(none)

Other Instances

Instance Parent
Enterprise OpenUP (with CobiT)Inception Iteration [1..n]Identify and Refine Requirements (Inception Iteration [1..n])
Enterprise OpenUP (with CobiT)Elaboration Iteration [1..n]Identify and Refine Requirements (Elaboration Iteration [1..n])